Hold The Horde — Campaign Evidence and State Crosswalk

This index maps the eight chains and fifteen primary cast scenes onto the rooms, controls, objects and observations they consume, and records where those interfaces agree or conflict. It covers 8 chains (L1–L4, S1–S4), 15 primary scenes (Y1–Y3, A1–A3, D1–D3, M1–M3, I1–I3), 26 evidence index entries, 7 mutually exclusive rescue host variants, 5 Story and Ending Map personal variants and 2 dependency orders.

0. Identifier provenance

Established identities: scene IDs Y1–I3 belong to Cast and Short Rescue Map; R01–R40 and M01–M24 to Station Room and Module Inventory; objective numbers 1–12 to Regional Discovery Map. L1–L4 and S1–S4 are index labels here for the four numbered chains in Two Language Discovery Map and Story and Ending Map respectively. Station Room and Module Inventory already uses L2 as shorthand for the second language chain.

Evidence aliases: every A-… key below is an index handle for observations in the cited source descriptions. The source-owner table below names those descriptions and the player decisions they inform. A handle can group the readings needed for one comparison; it is not a promise that the game captures a whole sequence in one action.

1. Chain and scene identity map

Scenes carry chain positions many-to-many. Story and Ending Map does not allocate its personal variants exclusively to one chain each:

Host variants (7). R13 hosts Y1 or A1, never both; the other person takes R19 pressure annex (Yeva) or R22 supply booth (Aster). Abort hosts are the four rooms R06, R12, R24 and R27.

2. Deduplicated evidence and knowledge ledger

One entry per observation; a shared observation is listed once with its separate consumers.

One observation, several kinds of consumer. A-TRANSFER feeds L3 as a role distinction and S3 as movement evidence; A-REPLY feeds L4 as register evidence and S2/S4 as evidence about what the line is; A-PROFILE feeds S2 causally and Y3/M3 as something a person reacts to. Shared observations are reused; distinct stages still require their own captures.

The chronology is three records. A-STRIP, A-CARD and A-BERTH share explicit cross-references and together support old seal state → human profile installation → current docking registration for these records only. The player compares them in the paused journal; nothing declares the chronology true, and no diagnostic reads history.

Each comparison needs its own observations. The initial side-by-side active-profile/bypass test needs both committed outcomes; it has no additional earlier-capture prerequisite. Comparing behavior before and after isolation does require a before-capture the player actually made. Two post-isolation results establish only current disconnection. No prior record is generated retroactively.

Source owners and decisions

These links own the underlying descriptions. A record referenced by multiple rows is still the same record.

3. Representative state and commit boundaries

Three separations. Holding an inference is not informing a survivor — a player may hold a correct reading indefinitely while everyone aboard still knows nothing. This is not an extra gate: where a scene's own design is to show the evidence, the showing inside that scene is the informing, and no separate prior step is required. A control responding is not proof of identity or history — A-REPLY shows that something answers, never who. Physical network completion is not an ending theory — objective 12 is a walkable fact independent of objective 10, rescue, treatment and any ending; what the core contains is S4, and neither settles the other.

Optional help. No chain depends on it: L1–L4 are solvable with no person aboard. Yeva may name the crew roads and Dorn may describe crawl-mark use, each only when shown a record, each attributed with its basis, and neither reads an alien script or knows current topology. Help is not withheld to protect an intended deduction.

4. The two dependency orders

These are Regional Discovery Map's two viable orders. The arrows are dependency priorities, not corridors; current access can interleave eligible objectives, and either order can defer R-3 until its short geometry exists.

Build-and-ship first — 1 → 2 → 3 → 4 → 8 → 6 → 10, then 5 → 7 → 9 → 11 → 12. Objective 1 supplies A-INSTALLED at R02/R03 and A-BERTH; the first death makes routes historical while those facts stay current, which is S1's whole opening. Objectives 2, 3, 4 and 8 earn movement, impact and positional parts and expose the physical wall/panel/slab differences used by L2 at 1 and 8, before systematic language comparison. Seeing those differences does not automatically grant their interpretation. Objective 6 completes without language, from gauges and the long access, so A-R18SEAL, A-CYCLE and D1 are available before L2's shortcut is understood; 10 then exposes the apparent-departure preparation. Only afterwards do 5, 7 and 9 supply A-RUNS, A-TAAN, A-TRANSFER, A-AB, A-ADDRESS and A-REPLY, which reinterpret evidence already stored rather than unlocking it. Objective 11 asks for the same physical pressure-equalisation action it always asks for; the language routes make it predictable, never optional. Objective 12 depends on placement and a selected joining rule — not on 10, rescue, treatment or an ending.

Language-and-network first — 1 → 5 → 7 → 3 → 6 → 9 → 4 → 8 → 11 → 2 → 10 → 12. Riskier observation comes early: 5 and 7 give L1/L3 before most parts exist, and tested predictions shorten 6 and 9. Objective 4 arrives late, so R-3 and its rescue wait for a current short geometry — and no chain stalls, because 5, 7, 9 and 11 never require a survivor. Objective 11's iris is reached before the ship assemblies are complete; the physical action is identical. A-STRIP is therefore available early here and late in the other order, which changes when the three-record chronology can be assembled but not what it supports.

What differs, and what does not. No chain changes hands and no evidence changes meaning between the orders; what changes is when a record becomes available to compare and how much reinterpretation happens after the fact. Rescues and survivor help are optional in both.

Yeva-first versus Aster-first is a compact subcase of either order. It selects which person occupies R13 and which takes the R19 annex or R22 booth, and therefore which follow-up scene appears early. It changes no objective sequence, no evidence and no chain.

5. Four contrary cases

1 — Retained evidence, changed access. A-WALLMARK from R17 survives death with its place and life; the route to R17 is historical. The mark's meaning is unaffected, but whether that wall is passable now is current-only and needs a fresh visit.

2 — Wrong interpretation, concrete correction. From two A-TRANSFER pairs the player reads the recurring token as source. The corrective third pair at R23 shows the same token at a receiving end. The correction is physical and self-administered: nothing says "wrong", the earlier note keeps its original wording in revision history, and which continuation to investigate changes on the player's own reading.

3 — Absent versus uninformed participant. A-PROFILE is committed. If Dorn was never rescued, Y3 has no Dorn variant and nothing is lost invisibly. If Dorn is aboard but has not been shown the comparison, he is present and uninformed — a different state, and his knowledge does not update by proximity.

4 — Apparent versus deeper ending, with the departure branch unselected. Objective 10's assemblies can make readiness true with no language, survivor or core answer. The deeper transaction at R40 is separate and does not require it. Story and Ending Map recommends an irreversible apparent-credit departure — leaving the field ending revival and closing station exploration in this continuity — against the alternative of keeping readiness as a repair milestone with no departure at all, and the outline treats field-limited revival and irreversible departure as optional assumptions. Objective 12 neither triggers nor blocks either.

6. Cross-reference notes

Personal variants in Story and Ending Map are scene variants, not chain numbers: variants 1–5 correspond to S1, S2, S2+S4, S3 and S2+S4. Core-related positions appear within M3 and I3; the shared profile scene is Y3 with Dorn participating when present.

The wall-access chain uses R04, the R15 edge, R17 and the R26 slab. Two Language Discovery Map owns that evidence chain.

Quantities. Mechanical Interfaces and Opening Quantities supplies the current comparison values: 10 C shared carrying capacity, a 12 O integral suit tank outside C/A, an ordinary-full canister of 8 O in a 2 C vessel and a prepared-full of 12 O in the same vessel, with conserved incremental transfer. Each rescue route still needs its own full-attempt return mark.

Open questions

• The safeguard where a survivor mid-crossing walks alone to a refuge with enemies frozen is pending owner decision; the Send row's world outcome depends on it.
• The departure branch is unselected: Story and Ending Map recommends an irreversible apparent-credit departure (leaving the field ends revival and closes station exploration in this continuity) against keeping readiness as a repair milestone with no departure at all.
• Save policy is a further open question; the departure-branch choice is not reducible to it.
• The five owner questions this index depends on remain unanswered.
• These rules are untested; numbers are proposals.